Failover procedure for networks

ABSTRACT

In an example embodiment, there is disclosed an apparatus comprising a plurality of ports and routing logic coupled with the plurality of ports. The routing logic obtains data representative of a first port configuration for the plurality of ports, the first port configuration comprises data representative of a status for individual ports selected from the plurality of ports, the status indicating whether an individual port selected from the plurality of ports is an open port, an alternate port, or a failed port. The routing logic forwards data in accordance with the first port configuration. The routing logic also obtains data representative of an alternate port configuration for the plurality of ports, the alternate port configuration is to be employed upon determining a predefined link has failed. The alternate configuration comprising a new status for individual ports selected from the plurality of ports.

TECHNICAL FIELD

The present disclosure relates generally to network availability.

BACKGROUND

Many protocols, such as a Spanning Tree Protocol (STP), are employed todetermine appropriate routes for network traffic. In determining theappropriate routes, the protocols may block certain links in an attemptto prevent looping of packets, which may be referred to as a networkstorm. These protocols may take seconds to converge, which may beacceptable during network startup. However, during operation, when anevent occurs that changes the topology of a network, such as a linkfailure, the protocol must re-converge and delays of this magnitude canbe seriously disruptive due to packet loss during the reconvergencetime. For example, applications with strict Quality of Service (QoS)constraints, such as voice over internet protocol (VoIP), may fail. Forexample, a VoIP call could be dropped.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings incorporated herein and forming a part of thespecification illustrate the example embodiments.

FIG. 1 is a block diagram illustrating an example of a switching deviceupon which an example embodiment may be implemented.

FIG. 2 is a block diagram illustrating an example of a device fordetermining a network topology, the appropriate links for the topologyand a failover configuration for the network topology.

FIG. 3 is a block diagram of a computer system upon which an exampleembodiment may be implemented.

FIG. 4 is a block diagram of a ring network for illustrating an exampleembodiment.

FIG. 5 is a block diagram illustrating an example of a spanning treenetwork topology as initially configured.

FIG. 6 illustrates an example of a link failure in the spanning treenetwork illustrated in FIG. 5.

FIG. 7 illustrates an example of the configuration of the spanning treenetwork after employing a predetermined alternate configuration inresponse to the link failure illustrated in FIG. 6.

FIG. 8 illustrates an example of a methodology for performing failoverin response to a link failure.

FIG. 9 illustrates an example of a methodology for configuring anetwork.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

The following presents a simplified overview of the example embodimentsin order to provide a basic understanding of some aspects of the exampleembodiments. This overview is not an extensive overview of the exampleembodiments. It is intended to neither identify key or critical elementsof the example embodiments nor delineate the scope of the appendedclaims. Its sole purpose is to present some concepts of the exampleembodiments in a simplified form as a prelude to the more detaileddescription that is presented later.

In accordance with an example embodiment, there is disclosed herein anapparatus comprising a plurality of ports and routing logic coupled withthe plurality of ports. The routing logic obtains data representative ofa first port configuration for the plurality of ports, the first portconfiguration comprises data representative of a status for individualports selected from the plurality of ports, the status indicatingwhether an individual port selected from the plurality of ports is anopen port, an alternate port, or a failed port. The routing logicforwards data in accordance with the first port configuration. Therouting logic also obtains data representative of an alternate portconfiguration for the plurality of ports, the alternate portconfiguration is to be employed upon determining a predefined link hasfailed. The alternate configuration comprising a new status forindividual ports selected from the plurality of ports.

In accordance with an example embodiment, there is disclosed herein,logic encoded in a non-transitory tangible computer readable medium forexecution by a processor and when executed operable to determining atopology of a network. The logic determines a first configuration basedon the topology, the first configuration comprising data representativeof open ports and alternate ports for a routing device coupled with thenetwork. The logic also determines an alternate configuration based onthe topology, the alternate configuration comprising data representativeof open ports and alternate ports for the routing device to use inresponse to a predefined link failing.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

This description provides examples not intended to limit the scope ofthe appended claims. The figures generally indicate the features of theexamples, where it is understood and appreciated that like referencenumerals are used to refer to like elements. Reference in thespecification to “one embodiment” or “an embodiment” or “an exampleembodiment” means that a particular feature, structure, orcharacteristic described is included in at least one embodimentdescribed herein and does not imply that the feature, structure, orcharacteristic is present in all embodiments described herein.

In an example embodiment, there is disclosed herein a technique forhandling link failures in a network. During the initial configuration,devices are initially connected with ports in the blocking state. Adevice such as a server, or devices, in the network build a map of thetopology of the network using a routing protocol. Any suitable routingprotocol that can determine the topology of the network may be employed.A protocol, such as Multiple Spanning Tree (MST), is employed to createa topology that is free of loops.

During the configuration process, a failover topology is calculated. Thefailover topology determines a response to a link failure. In particularembodiments, the failover topology will determine responses for multiplelink failures. For example, a protocol such as IS-IS (IntermediateSystem to Intermediate System—RFC 1142) can be used to allow devices inthe topology to learn the topology of the whole network. The deviceswould be able to calculate failover scenarios, as an alternative to amaster device calculating the failover scenarios and then distributingthem to the devices.

Link failure can be detected using any suitable technique. For example,Physical Layer (PHY) devices can detect link failure. In particularembodiments, the PHY may be polled. In an example embodiment, linkfailure can be detected based on hello packets. For example, a portsends to its link partner one packet per a predetermined (programmable)time period. The port sets an interrupt when no hello packet is receivedin three programmable time periods. Further, when the port detects linkfailure, the port generates a multicast packet, referred to herein as aHardware Flood Layer (HFL) packet, which is employed to announce thelink failure to devices in the network.

A device receiving an HFL notification will forward the notification toother ports coupled with the topology as well as to its own CentralProcessing Unit (CPU) and/or in a stack environment, other CPUs in astack. Based on data representative of where the failure occurred in theHFL notification, a device receiving the HFL may add a port (or unblocka previously blocked port), delete a port (or change a port to a blockedstate), or do nothing, In the event of Virtual Local Area Network (VLAN)load balancing across multiple ports, if a port fails the load can bedistributed among the remaining ports (e.g., if two ports are used forVLAN balancing and one of the ports fails, VLAN traffic may be re-routedto the remaining port).

FIG. 1 is a block diagram illustrating an example of a switching device100 upon which an example embodiment may be implemented. The switchingdevice 100 comprises routing logic 102 that determines how packetsshould be routed. “Logic”, as used herein, includes but is not limitedto hardware, firmware, software and/or combinations of each to perform afunction(s) or an action(s), and/or to cause a function or action fromanother component. For example, based on a desired application or need,logic may include a software controlled microprocessor, discrete logicsuch as an application specific integrated circuit (“ASIC”), system on achip (“SoC”), programmable system on a chip (“PSOC”), aprogrammable/programmed logic device, memory device containinginstructions, or the like, or combinational logic embodied in hardware.Logic may also be fully embodied as software stored on a non-transitory,tangible medium which performs a described function when executed by aprocessor. Logic may suitably comprise one or more modules at one ormore locations configured to perform one or more functions. For example,the routing logic 102 may suitably comprises a host processor andsoftware for performing the functionality described herein. In anexample embodiment, the routing logic 102 comprises forwarding tablesfor determining how to route packets.

The switching device 100 comprises a plurality (or N) of ports 104-1through 104-N, where N is an integer greater than one. For example, in Nmay be two (e.g., in a ring network), or N may be as high as isphysically realizable (e.g., in a spanning tree network or other anyother network topology including a ring network). The routing logic 102can selectively route data through port-1 104-1 via path 108 and/orthrough port 104-N via path 110. A port may be considered an open port,an alternate (or blocked) port, or a failed port. An open port is a portthat is forwarding traffic. An alternate (or blocked) port is anoperational port that is blocked, e.g., traffic is not being forwarded.A failed port is a port with a non-operational link status. Ports 104-1,104-N may be wired ports, wireless ports, or a combination of wired andwireless ports.

In an example embodiment, the routing logic 102 obtains datarepresentative of a first port configuration for the plurality of ports104-1, 104-N. The first port configuration comprises data representativeof a status for individual ports selected from the plurality of ports,the status indicating whether an individual port selected from theplurality of ports is an open port, an alternate port, or a failed port.The routing logic 102 forwards data in accordance with the firstconfiguration. The routing logic 102 also obtains data representative ofan alternate port configuration for the plurality of ports 104-1, 104-N.The alternate port configuration is to be employed upon determining apredefined link has failed. The alternate configuration comprises a newstatus for individual ports selected from the plurality of ports.

In an example embodiment, the routing logic 102 switches to thealternate port configuration in response to determining the predefinedlink has failed. The notification of the failed link is propagatedthough open ports and alternate ports selected from the plurality ofports 104-1, 104-N.

In an example embodiment, the predefined link is connected to a selectedone of the plurality of ports 104-1, 104-N. The routing logic 102switches to the alternate port configuration in response to detectingthe predefined link has failed. The routing logic generates thenotification of the failed link that is propagated through the openports and alternate ports. In an example embodiment, a failed link isdetected by polling the selected one of the plurality of ports. Inanother example embodiment, a failed link is detected in response to notreceiving a predefined packet at the selected one of the plurality ofports for more than a predefined time period. For example, if a “hello”packet has not been received for a time period, which may comprise aplurality of periodic and/or aperiodic intervals, the routing logic 102determines the link has failed.

In an example embodiment, the routing logic 102 receives a predefinedpacket indicating the predefined link has failed. For example, a HFLpacket as described herein supra may be employed. In particularembodiments, the predefined packet comprises data representative of anidentifier for the failed link.

In an example embodiment, the routing logic 102 stops forwarding trafficin response to determining the predefined link has failed. The routinglogic 102 waits for a predetermined time period after determining thepredefined link has failed before forwarding traffic as specified by thealternate port configuration.

In an example embodiment, the routing logic 102 obtains datarepresentative of a second alternate port configuration to be employedin response to a second link failing while employing the first alternateconfiguration. The routing logic 102 may receive the data representativeof a second alternate port configuration from another device or maydetermine the second alternate port configuration itself. In particularembodiments, the routing logic 102 waits for a specified time periodbefore determining the second alternate port configuration.

In an example embodiment, the data representative of a firstconfiguration and the data representative of an alternate configurationcomprise separate port statuses for individual ports selected from theplurality of ports on a per virtual local area network (VLAN) basis fora plurality of VLANs. For example, port 104-1 may be open port for afirst VLAN but an alternate (blocked) port for a second VLAN. Inparticular embodiments, multiple ports may be employed for a VLAN forload balancing.

In an example embodiment, the routing logic 102 determines a topology ofa network coupled with the plurality of ports 104-1, 104-N. For example,routing logic 102 may send and receive packets requesting devicescoupled to a port respond with their address and addresses of anydevices they detect on their ports. The routing logic 102 determines thefirst configuration and alternate configuration based on the topology.

In an example embodiment, the alternate port configuration may suitablycomprise a plurality of alternate configurations. For example, the datarepresentative of an alternate port configuration may suitably comprisedata representative of a first alternate port configuration to beemployed upon determining a first predefined link has failed, and datarepresentative of a second alternate port configuration to be employedupon determining a second predefined failed link. Thus, the datarepresentative of an alternate port configuration comprises datarepresentative of a plurality of alternate port configurationscorresponding to a plurality of predefined link failures.

In an example embodiment, a failover signal 112 may be employed forindicating when a link has failed. The failover signal 112 may be asignal that is asserted by a port receiving a notification of a failedlink or by the routing logic 102 in response to determining a linkattached to one of ports 104-1, 104-N has failed. In an alternativeembodiment, the failover signal 112 may be a register or latch that isset. The failover signal 112 may be cleared after a predetermined timeperiod or event. For example, the failover signal 112 may be clearedafter new alternate configurations are determined.

FIG. 2 is a block diagram illustrating an example of a device 200 fordetermining a network topology, the appropriate links for the topologyand a failover configuration for the network topology. Device 200 may beimplemented by a server or be embodied in a routing device such as aswitch and/or router. In the illustrated example, the device 200comprises an interface 202 coupled with a link 204 that allows forcommunications with external devices, such as other routing devicescoupled with a network. Interface may be any suitable wired and/orwireless interface.

In an example embodiment, the topology module 206 sends packetscomprising data representative of other devices detected on link 204 byinterface 202. In addition, topology module 206 receives packets fromother devices via interface 202 that comprise data representative ofdevices the other devices detected on their ports. Based on the datareceived from the other devices and other devices detected on link 204by interface 202, the topology module 206 determines a topology for thenetwork.

The port configuration module 208 determines from the topology a firstport configuration for devices on the network. In an example embodiment,the topology module 206 determines a configuration that is free of loopsto prevent network storms.

The port configuration module 208 determines an alternate portconfiguration for the devices on the network. The alternateconfiguration assumes a particular link has failed and is aconfiguration to be employed in the event the particular link fails. Inparticular embodiments, the port configuration module 208 determines aplurality of alternate port configurations. The plurality of alternateport configurations correspond to a plurality of different link failurescenarios.

FIG. 3 is a block diagram of a computer system 300 upon which an exampleembodiment may be implemented. Computer system 300 is suitable forimplementing the route control logic 102 described in FIG. 1, thetopology module 206 described in FIG. 2, and/or the port configurationmodule 208 described in FIG. 2.

Computer system 300 includes a bus 302 or other communication mechanismfor communicating information and a processor 304 coupled with bus 302for processing information. Computer system 300 also includes a mainmemory 306, such as random access memory (RAM) or other dynamic storagedevice coupled to bus 302 for storing information and instructions to beexecuted by processor 304. Main memory 306 also may be used for storinga temporary variable or other intermediate information during executionof instructions to be executed by processor 304. Computer system 300further includes a read only memory (ROM) 308 or other static storagedevice coupled to bus 302 for storing static information andinstructions for processor 304. A storage device 310, such as a magneticdisk, optical disk, and/or flash storage, is provided and coupled to bus302 for storing information and instructions.

An aspect of the example embodiment is related to the use of computersystem 300 for implementing a failover procedure for networks. Accordingto an example embodiment, implementing the failover procedure fornetworks is provided by computer system 300 in response to processor 304executing one or more sequences of one or more instructions contained inmain memory 306. Such instructions may be read into main memory 306 fromanother computer-readable medium, such as storage device 310. Executionof the sequence of instructions contained in main memory 306 causesprocessor 304 to perform the process steps described herein. One or moreprocessors in a multi-processing arrangement may also be employed toexecute the sequences of instructions contained in main memory 306. Inalternative embodiments, hard-wired circuitry may be used in place of orin combination with software instructions to implement an exampleembodiment. Thus, embodiments described herein are not limited to anyspecific combination of hardware circuitry and software.

The term “computer-readable medium” as used herein refers to any mediumthat participates in providing instructions to processor 304 forexecution. Such a medium may take many forms, including but not limitedto non-volatile media, and volatile media. Non-volatile media includefor example optical or magnetic disks, such as storage device 310.Volatile media include dynamic memory such as main memory 306. As usedherein, tangible media may include volatile and non-volatile media.Common forms of computer-readable media include for example floppy disk,a flexible disk, hard disk, magnetic cards, paper tape, any otherphysical medium with patterns of holes, a RAM, a PROM, an EPROM, aFLASHPROM, CD, DVD or any other memory chip or cartridge, or any othermedium from which a computer can read.

Computer system 300 also includes a communication interface 318 coupledto bus 302. Communication interface 318 provides a two-way datacommunication coupling computer system 300 to a network link 320 that isconnected to a local network 322. Communication interface 318 allowsprocessor 304 to send and receive messages regarding the networktopology and/or network failovers. For example, processor 304 mayreceive data representative of a failed link via communication interface318. In particular embodiments, computer system may suitably comprisemultiple communication interfaces 318 which may be coupled to one ormore networks or one more segments of a network.

FIG. 4 is a block diagram of a ring network 400 for illustrating anexample embodiment. Switches 402 and 404 are coupled via link 406.Switches 404 and 408 are coupled via link 410. Switch 404 is alsocoupled with switch 412 via link 414. Switches 408 and 412 are coupledvia link 418. Switch 412 is also coupled with switch 402 via link 416.In the illustrated example, in order to prevent looping or networkstorms, ports coupled with links 414 and 416 are configured to be in analternate (blocked state).

Alternate configurations can be generated based on various linkfailures. For example, if link 406 fails, an alternate configuration canbe employed where ports coupled to links 414 and 416 can be changed tothe open state. If link 410 fails, an alternate configuration can beemployed where ports coupled with link 414 are changed to the openstate, while ports coupled to link 416 remain in the alternate (blocked)state. If link 418 fails, an alternate configuration can be employedwhere ports coupled with links 414 and 416 are changed to the openstate. In particular embodiments, multiple link failures may beaccommodated. For example, if links 406 and 418 fail, an alternate portconfiguration opening ports coupled with links 414 and 416 can beemployed.

FIG. 5 is a block diagram illustrating an example of a spanning treenetwork 500 topology as initially configured. In the illustratedexample, switch 502 is coupled with switch 504 via link 506. Switch 502is also coupled with switch 508 via link 510. Switch 508 is coupled withswitch 512 via link 514. Switch 508 is coupled with switch 516 via link518. Switch 516 is also coupled with switch 520 via link 522. Switch 520is coupled with switch 508 via link 524. Switch 504 is also coupled withswitch 512 via link 526. Links 506, 510, 514, 518, 522, 524, and 526 maysuitably comprise wired, wireless, and or a combination of wired andwireless links. In the illustrated example, links 510, 514, 518, 524,and 526 are in the open state, and links 506 and 522 are in thealternate (blocked) state to prevent looping. The switches 502, 504,508, 512, 516, and 520 also obtain an alternate configuration. Thealternate configuration may be provided to the switches 502, 504, 508,512, 516, and 520, or the switches 502, 504, 508, 512, 516, and 520 maycalculate the alternate configurations.

For example, the switches 502 and 504 may employ an alternateconfiguration where the ports coupled with link 506 switch from thealternate to the open state if links 506, 510, and/or 514 fail. Analternate configuration may be employed where switches 516 and 520switch the ports coupled with link 522 to the open state in response todetecting a failure of link 518 and/or 524.

FIG. 6 illustrates an example of the state 600 of the spanning treenetwork 500 illustrated in FIG. 5 when link 514 fails. In response tothe failure, switches 512 and 508 generate link failure notificationsignals and send them on their non-failed (e.g., open and alternate)ports. For example, switch 508 would propagate the notification on links510, 518 and 524 while switch 512 would propagate the failure on link526. The notification would be propagated throughout the network. Inparticular embodiments, the notification would include data identifyingthe failed link, link 514 in this example.

In an example embodiment, the switches 502, 504, 508, 512, 516, and 520in response to detecting the link failure or receiving a notification ofthe link failure, would enter a “quiet period” where the switches 502,504, 508, 512, 516, and 520 would stop forwarding packets for apredefined time period. In an example embodiment, a predefined timeperiod is selected that would allow for the notification to propagatethroughout the network and for devices to connect to the alternateconfiguration.

FIG. 7 illustrates an example of the configuration 700 of the spanningtree network 500 after employing a predetermined alternate configurationin response to the link failure illustrated in FIG. 6. In theillustrated example, switches 502 and 504 switch the ports coupled withlink 506 to the open state to allow traffic on link 506 that waspreviously in the alternate (blocked) state. In an example embodiment,the switches 502, 504, 508, 512, 516, and 520 will flood packets (exceptfor on the ports the packet was received on) until the addresses of theswitches 502, 504, 508, 512, 516, and 520 are flushed from theForwarding tables and relearned on the new topology 500. For example,switch 502 may flood packets onto links 506 and 510 and switch 504 mayflood packets onto link 506 and 526. In particular embodiments, switchesthat were not affected by the link failure and/or did not have anyconfiguration changes, such as switches 516 and 520 and 504 may continueoperation without flooding packets.

In view of the foregoing structural and functional features describedabove, methodologies in accordance with example embodiments will bebetter appreciated with reference to FIGS. 8 and 9. While, for purposesof simplicity of explanation, the methodologies of FIGS. 8 and 9 areshown and described as executing serially, it is to be understood andappreciated that the example embodiments are not limited by theillustrated orders, as some aspects could occur in different ordersand/or concurrently with other aspects from that shown and describedherein. Moreover, not all illustrated features may be required toimplement the methodologies described herein. The methodologiesdescribed herein are suitably adapted to be implemented in hardware,software, or a combination thereof.

FIG. 8 illustrates an example of a methodology 800 for performingfailover in response to a link failure. Methodology 800 may be performedby routing logic 102 (FIG. 1) and logic embodied in ports 104-1 and104-N (FIG. 1), and/or processor 304 (FIG. 3). Moreover, methodology 800may be implemented by any of switches 402, 404, 408, and/or 412 (FIG. 4)and/or any of switches 502, 504, 508, 512, 516, and/or 520 (FIG. 5).

At 802 an initial configuration is obtained. The initial configurationmay be obtained from an external device such as a server or masterswitch, or a device may determine the topology of the network and theinitial configuration. For example, the device may send packetsidentifying the device and neighboring devices detected on the device'sports. The device may also receive packets from neighboring devices thatidentify device's the neighboring devices have detected as well aspackets the neighboring devices received from other devices.

At 804, a determination is made whether a local link has failed. Adetermination may be made by detecting a link coupled with a port hasfailed, for example by polling the port and/or waiting for predeterminedmessages over a predetermined time period. The predetermined time periodmay suitably comprise a plurality of periodic and/or aperiodicintervals.

If a local link is not up (NO), processing skips to 806; otherwise, at805 a determination is made whether a notification has been receivedthat a remote link has failed from a neighboring device. The predefinedpacket, such as a HFL may be received from a neighboring device coupledwith any open and/or alternate port. In particular embodiments, thenotification comprises data representative of where the link failureoccurred. If, at 805, no notification was received of a failed link(NO), 804 and 805 are repeated (either continuously or at predefinedintervals). If, however, at 805, a notification was received that aremote link has failed (YES), processing continues at 806.

At 806, a notification of the link failure is forwarded. The linkfailure notification is forwarded on non-failed (e.g., open and/oralternate) ports. If the link failure was received from a neighboringdevice, the notification is not forwarded onto the port where thenotification was received.

At 808, forwarding of traffic is halted for a predefined time period. Inan example embodiment, the time period is selected to allow sufficienttime for notification packets to propagate throughout the network.

At 810, a determination is made where the link failure occurred. In anexample embodiment, the determination is based on data received in thelink failure notification.

At 812, a previously obtained alternate configuration for that isappropriate remedying the failed link is implemented. A device's portsare adjusted in accordance with the appropriate alternate configuration.For example, based on the alternate configuration, previously blockedports may be opened to allow traffic and/or previously opened ports maybe closed, or the ports may remain unchanged.

At 814, traffic is forwarded in accordance with the alternateconfiguration. After a predefined time period, new alternateconfigurations may be determined for handling a failover for the current(alternate) topology. Packets may be flooded onto the network until theappropriate forwarding paths are determined.

FIG. 9 illustrates an example of a methodology 900 for configuring anetwork. The methodology 900 may be implemented by device 200 (FIG. 2)and/or processor 304 (FIG. 3).

At 902, the network topology is determined. In an example embodiment,devices on the network sends packets comprising data identifying thedevice sending the packet and data representative of neighboring devicesthat the device has detected, and on which ports. Based on the receiveddata, the topology for the network can be determined. Moreover, data maybe obtained that indicates whether the network is a ring, star, mesh orother network.

At 904, links for the topology are determined. The status of the links,open or alternate (blocked) are selected in order to prevent looping ornetwork storms.

At 906, alternate paths are determined for remedying link failures. Forexample, based on a certain link failing, which ports should be openedand/or blocked that will allow the network to function while preventingnetwork loops. A plurality of alternate configurations corresponding toa plurality of potential link failures may be determined.

At 908, the alternate configurations are distributed to nodes on thenetwork. In an example embodiment, if an alternate configuration becomesthe active configuration for the network, new alternate configurationscan be determined for the network and distributed to the nodes on thenetwork.

Described above are example embodiments. It is, of course, not possibleto describe every conceivable combination of components ormethodologies, but one of ordinary skill in the art will recognize thatmany further combinations and permutations of the example embodimentsare possible. Accordingly, this application is intended to embrace allsuch alterations, modifications and variations that fall within thespirit and scope of the appended claims interpreted in accordance withthe breadth to which they are fairly, legally and equitably entitled.

The invention claimed is:
 1. An apparatus, comprising: a plurality ofports in mutual operative communication via a plurality of associatedlinks interconnecting the plurality of ports; routing logic coupled withthe plurality of ports, the routing logic selectively routing data tothe plurality of ports via the plurality of associated links; whereinthe routing logic obtains data representative of a first portconfiguration for the plurality of ports, the first port configurationcomprising data representative of a status for a set of individual portsselected from the plurality of ports, the status indicating whether anindividual port selected from the plurality of ports is an open port, analternate port, or a failed port; wherein the routing logic forwards thedata in accordance with the first configuration; and wherein the routinglogic obtains data representative of an alternate port configuration forthe plurality of ports, the alternate port configuration to be employedupon determining a predefined link of the plurality of associated linkshas failed, the alternate configuration comprising a new status for theset of individual ports selected from the plurality of ports.
 2. Theapparatus set forth in claim 1, wherein the routing logic switches tothe alternate port configuration in response to determining thepredefined link has failed; and wherein a notification of the failedlink is propagated though open ports and alternate ports selected fromthe plurality of ports.
 3. The apparatus set forth in claim 2, whereinthe predefined link is connected to a selected one of the plurality ofports; wherein the routing logic switches to the alternate portconfiguration in response to detecting the predefined link has failed;and wherein the routing logic generates the notification of the failedlink that is propagated through the open ports and alternate ports. 4.The apparatus set forth in claim 3, wherein the failed link is detectedby polling the selected one of the plurality of ports.
 5. The apparatusset firth in claim 3, wherein the failed link is detected in response tonot receiving a predefined packet at the selected one of the pluralityof ports for more than a predefined time period.
 6. The apparatus ofclaim 2, wherein the routing logic receives a predefined packetindicating the predefined link has failed.
 7. The apparatus set forth inclaim 2, wherein the predefined packet comprises data representative ofan identifier for the failed link.
 8. The apparatus set forth in claim2, wherein the routing logic stops forwarding traffic in response todetermining the predefined link has failed; and wherein the routinglogic waits for a predetermined time period after determining thepredefined link has failed before forwarding traffic as specified by thealternate port configuration.
 9. The apparatus set forth in claim 2,wherein the routing logic stops forwarding traffic in response todetermining the predefined link has failed; wherein the routing logicwaits for a predetermined time period after determining the predefinedlink has failed before forwarding traffic; and wherein the routing logicforwards traffic in accordance with the first port configuration inresponse to determining the failed link has healed before thepredetermined time period expired.
 10. The apparatus set forth in claim2, wherein the routing logic obtains data representative of a secondalternate port configuration to be employed in response to a second linkfailing while employing the first alternate configuration.
 11. Theapparatus set forth in claim 1, wherein the data representative of afirst configuration and the data representative of an alternateconfiguration comprise separate port statuses for individual portsselected from the plurality of ports on a per virtual local area networkbasis for a plurality of virtual local area networks.
 12. The apparatusset forth in claim 1, wherein the routing logic determines a topology ofa network coupled with the plurality of ports; and the routing logicdetermines the first configuration and alternate configuration based onthe topology.
 13. The apparatus set forth in claim 1, wherein the datarepresentative of an alternate port configuration comprises datarepresentative of a first alternate port configuration to be employedupon determining a first predefined link has failed, and datarepresentative of a second alternate port configuration to be employedupon determining a second predefined failed link.
 14. The apparatus setforth in claim 1, wherein the data representative of an alternate portconfiguration comprises data representative of a plurality of alternateport configurations corresponding to a plurality of predefined linkfailures.
 15. Logic encoded in a non-transitory tangible computerreadable medium for execution by a processor and when executed operableto: obtain data representative of a first port configuration for aplurality of ports in mutual operative communication via a plurality ofassociated links interconnecting the plurality of ports, the first portconfiguration comprising data representative of a status for a set ofindividual ports selected from the plurality of ports, the statusindicating whether an individual port selected from the plurality ofports is an open port, an alternate port, or a failed port; forward datain accordance with the first configuration; and obtain datarepresentative of an alternate port configuration for the plurality ofports, the alternate configuration to be employed upon the detection ofa failure for a predefined link of the plurality of associated links,and the alternate configuration comprising a new status for the set ofindividual ports selected from the plurality of ports.
 16. The logicaccording to claim 15, further operable to: obtain a notification thatthe predefined link has failed; propagate the notification to open portsselected from the plurality of ports and alternate ports selected fromthe plurality of ports; and forward data in accordance with thealternate port configuration responsive to obtaining the notificationthat the predefined link has failed.
 17. The logic according to claim16, further operable to stop forwarding data in response to obtainingthe notification that the predefined link has failed; and wait for apredefined time period after obtaining the notification that thepredefined link has failed before forwarding data in accordance with thealternate port configuration.
 18. A method, comprising: obtaining byrouting logic of an associated apparatus data representative of a firstport configuration for a plurality of associated ports operativelycoupled with the associated routing logic and in mutual operativecommunication via a plurality of associated links interconnecting theplurality of ports, the first port configuration comprising datarepresentative of a status for a set of individual ports selected fromthe plurality of ports, the status indicating whether an individual portselected from the plurality of ports is an open port, an alternate port,or a failed port; obtaining by the routing logic data representative ofan alternate port configuration for the plurality of ports, thealternate configuration to be employed upon the detection of a failurefor a predefined link of the plurality of associated links, and thealternate configuration comprising a new status for the set ofindividual ports selected from the plurality of ports; and forwarding bythe routing logic data in accordance with the first port configurationwhile the predefined link is operational.
 19. The method according toclaim 18, further comprising: obtaining a notification that thepredefined link has failed; propagating the notification via open portsselected from the plurality of ports and alternate ports selected fromthe plurality of ports; and forwarding data in accordance with thealternate port configuration responsive to obtaining the notificationthat the predefined link has failed.
 20. Logic encoded in anon-transitory tangible computer readable medium for execution by anassociated processor and when executed by the associated processor thelogic being operable to: determine a topology of a network, the networkcomprising a plurality of routing devices in mutual operativecommunication via a plurality of associated links interconnecting theplurality of routing devices of the network; determine a first portconfiguration based on the topology, the first port configurationcomprising data representative of open ports and alternate ports for theplurality of routing devices coupled in the network; and determine analternate a port configuration based on the topology, the alternateconfiguration comprising data representative of open ports and alternateports for the plurality of routing devices to use in response to apredefined associated link of the plurality of associated links failing.